Itemized Receipts and Digital Payments System and Methods

ABSTRACT

Embodiments of the invention are directed to a computer-implemented expense splitting method and system for allowing a payer to divide expenses among multiple purchasers with merchant integration. The method may include storing, in at least one computer memory, payer data and expense splitting instructions and accessing the computer memory with at least one computer processor and executing the instructions to perform multiple steps. The steps may include converting a captured receipt image to purchase data and providing a user interface displaying entries corresponding to purchases, and further providing a tagging option for tagging each of the entries with an indicator of at least one purchaser identity. The steps may also include storing the receipt data and format for easy receipt capture on a subsequent purchase.

RELATED APPLICATIONS

This application is a Continuation-In-Part application of U.S. patentapplication Ser. No. 14/033,768, filed on Sep. 23, 2013, which is aContinuation-In-Part of U.S. patent application Ser. No. 13/165,929,filed on Jun. 22, 2011. This application is related to commonly assignedco-pending application Ser. No. 11/952,457, filed on Dec. 7, 2007 andU.S. patent application Ser. No. 13/795,147, filed on Mar. 12, 2013.Each of the above-referenced patent applications is incorporated hereinby reference in its entirety.

TECHNICAL FIELD

Embodiments of the invention are related to systems and methods forfacilitating management of expenses through capture and utilization ofinformation traditionally provided on paper point-of-sale (POS)receipts.

BACKGROUND OF THE INVENTION

Consumers have increasingly become “cashless” and are becoming moreinclined to use credit cards and other non-cash vehicles to pay forgoods and services. Furthermore, consumers have grown accustomed tomobile technologies and are often able to pay for goods and servicesthrough various applications on their smart phones, tablets, or otherdevices. Additionally, consumers and merchants alike expect more fromtheir technology, including technology that learns their habits andconfigurations and conforms accordingly.

While it may often be more convenient to make electronic payments thancash payments, it is often more difficult to split expenses betweengroup members with electronic payments. For example, when a group visitsa restaurant, each member may want to pay for only his or her portion ofthe bill. While some restaurants may split the check between multiplecredit cards, others may be reluctant to do so especially in view of theincreasing fees to the merchant for accepting multiple cards for onebill. Furthermore, while restaurants may be willing to split a billevenly, they typically will not allocate expenses so that each personpays for his or her own purchases and will not offer separate checks forvery large groups of customers. Thus, it is difficult for individuals toadhere to a budget when participating in a large group purchase.

Another problem arises due to lack of electronically providedinformation for record keeping, especially when consumers intend tosplit expenses, since detailed information is required to accuratelydivide the expenses. While businesses may issue paper receipts, whenconsumers make purchases with a credit card, the electronic records ofthe purchase include a POS transaction record and a credit card recordderived from the POS transaction record. Frequently, because the receiptis a paper receipt, it remains disjointed from and is never linked withany electronic purchase information. When purchases are made online, thereceipt from the merchant may be delivered electronically. However, whenpurchases are made in person, receipts are typically traditional paperreceipts. In either case, the receipt may include information that isnot readily available through POS records or through credit cardrecords. For example, the receipt may include specific informationrelated to goods or services purchased, whereas other records may merelyinclude general information such as a total amount charged, merchantidentifying information.

Furthermore, customers are then required to retain the receipt so thatthey can produce it upon returning a purchased item or upon exercising awarranty, or simply in order to keep an accurate record of expenses.Paper receipts can easily be lost or accidentally thrown away.Furthermore, with the availability of electronic record keeping, thedistribution of paper receipts creates unnecessary waste.

To overcome the difficulties explained above with respect to lostinformation on paper receipts and the lack of consolidation withelectronic receipts, systems have been proposed for capturing receiptimages, transforming the image information to data, and storing andotherwise operating on the transformed data. For example, co-pendingapplication Ser. No. 13/165,929, filed on Jun. 22, 2011, and Ser. No.13/795,147, filed on Mar. 12, 2013, both of which are incorporatedherein by reference, disclose methods for capturing the receipt data andintegrating it with existing expense management systems.

Accordingly, due to the above-mentioned deficiencies with currentlyexisting systems, a solution is needed for incorporating recentlydeveloped data capture technologies to reduce burdens associated withpaper receipts and improving expense management capabilities based onthe information contained in the paper receipts. A solution is neededfor minimizing dependence on paper receipts and facilitating expensemanagement by purchasers. Furthermore, a solution is needed that iscapable of implementing a captured receipt image for expediting andfacilitating splitting of expenses between customers. A solution is alsoneeded for quickly and efficiently allowing a party member tocommunicate with a merchant.

SUMMARY OF THE INVENTION

A computer-implemented expense splitting system and method for allowinga payer to divide expenses with a computer memory storing payer data andexpense splitting instructions, a computer processor accessing thecomputer memory and executing the instructions to perform stepsincluding: converting a captured receipt image to purchase data, storingthe captured receipt image format in a receipt vault, providing aninteractive user interface that displays a setting wherein a payerchooses a location at the setting, and a merchant's entriescorresponding to purchases, allocating a percentage of each entry to atleast one purchaser based on the tagging or the setting, calculating anamount due from each purchaser based on the allocation, and providing apayment interface for allowing online payment from the payer for a totalamount of purchase.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawings figures, wherein:

FIG. 1 is a block diagram illustrating an operating environment forexpense splitting and receipt management systems in accordance with anembodiment of the invention;

FIG. 2 is a block diagram illustrating an expense splitting applicationin accordance with an embodiment of the invention;

FIG. 3 is a flow chart illustrating an expense splitting method inaccordance with an embodiment of the invention;

FIG. 4 is a flow chart illustrating a payment processing methodperformed within an expense splitting method in accordance with anembodiment of the invention;

FIG. 5 is a work flow diagram illustrating a reimbursement processingmethod that may be implemented in accordance with an embodiment of theinvention;

FIG. 6 is a user interface illustrating a payment recipient list thatmay be implemented in accordance with an embodiment of the invention;

FIG. 7 is a user interface illustrating a method for receipt capture inaccordance with an embodiment of the invention;

FIG. 8 is a user interface illustrating an expense splitting method inaccordance with an embodiment of the invention;

FIG. 9 is a block diagram illustrating a receipt collection andmanagement system in accordance with an embodiment of the invention;

FIG. 10 is a work flow diagram illustrating receipt managementprocedures in accordance with an embodiment of the invention;

FIG. 11 is a work flow diagram illustrating procedures for creating atravel report in accordance with an embodiment of the invention;

FIG. 12 is a flow chart illustrating a method for receipt management inaccordance with an embodiment of the invention;

FIG. 13 is a block diagram illustrating an expense splitting applicationin accordance with an embodiment of the invention;

FIG. 14 is a diagram depicting an exemplary embodiment of a tablesetting in accordance with an embodiment of the invention;

FIG. 15 is a user interface illustrating various merchants in accordancewith an embodiment of the invention;

FIG. 16 is a user interface illustrating a menu in accordance with anembodiment of the invention;

FIG. 17 is a block diagram illustrating the merchant interface inaccordance with an embodiment of the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the invention provide a system for allocating each itemon a receipt for a purchase so that only the appropriate parties bearthe expense. Furthermore, embodiments of the invention enable theparties splitting the purchase to quickly and efficiently electronicallysettle their finances between one another. Embodiments of the presentinvention are further directed to a method and system for reducingburdens associated with paper receipts and improving expense managementcapabilities based on the information contained in the paper receipts.The system minimizes dependency on paper receipts and facilitatesexpense management by users. Embodiments of the invention are also drawnto machine learning and merchant integration. For example, machinelearning coupled with GPS and merchant information for parsing ofitemized receipts may be incorporated. Merchants are all persons orcompanies involved in trade on both a national and/or internationallevel, including for example, retailers, wholesalers, and serviceproviders. Though the disclosures herein focus on restaurants,embodiments of the invention apply in equal force to all merchants.Other technology that may be employed is iBeacon technology, forexample, wherein alerts for the application may be created when a useapproaches or leaves a location. Bluetooth Low Energy wirelesstechnology, or Bluetooth technology may also be employed.

Embodiments of the invention are capable of parsing all, or any, typesof receipts that are formatted in any way. Various attributes may beextracted such as, for example, quantity, item detail, price, andmerchant. In embodiments of the invention, once a particular receiptformat and information has been parsed, the computer, application, orother electronic machine can store the format in its memory and recalland process it for later uses. A user may set rules for parsingreceipts. Embodiments of the invention are fully customizable. Forexample, if a user seeks all items to be automatically categorized, arule may be set up for that. Persons of ordinary skill will recognizethe various rules that may be set up.

Furthermore, embodiments of the invention are able to provide a combinedproduct suite as a result of the resources and offerings supplied by thefinancial institution managing the system. Expense splittingfunctionality can be offered in combination with automated paymentfunctionality, such as Chase QuickPay™, and other components of themobile application. The automated payment functionality can be used bothto pay for a purchase and to reimburse payers for payment of purchases.The payment functionality may optionally incorporate a tokenizationsystem. The system may be implemented for dividing restaurant expenses,but also may be used to split grocery bills, recurring bills, orentertainment purchases. As examples, college students, youngprofessionals splitting expenses, or employees being reimbursed by theiremployers may benefit from the functionality provided by the system.Embodiments of the invention may be able to quickly, accurately, andeffectively associate an individual's purchases to the individual.Embodiments of the invention may also be applied in instances such assplitting a bill for a vacation or outing, or co-hosting an event. Forexample, two roommates wishing to throw a debate party, for example, mayuse the claimed invention for splitting their expenses. Employers mayalso employ embodiments of the invention for expenses. For example, amiddle school gym teacher can use the claimed invention to pay forarticles needed for gym class. Persons of ordinary skill wouldunderstand the various instances that require splitting of a billbetween multiple parties. Parties are inclusive of real and non-realpersons, such as, for example, organizations.

FIG. 1 is a block diagram illustrating an operating environment forexpense splitting and receipt management systems in accordance with anembodiment of the invention. A point of sale (POS) device 10 may beconnected over a network 40 with a transaction processing system 70 andover a network 50 with financial institution systems 100. The financialinstitution systems 100 may include a receipt management system 80,payment systems 90, and other systems known to be operated by financialinstitutions. Mobile devices 20 a . . . 20 b may also connect over thenetwork 50 with the financial institution systems 100 and the POS device10. System users may connect using computing devices 30 a . . . 30 cover a network 60 with the financial institution systems 100. Althoughmultiple networks are shown, a smaller or larger number of networks maybe provided. All of the system components may communicate over a singlenetwork, such as the Internet, with the financial institution systems100.

The POS device 10 may be disposed at the location where a transactionoccurs. A POS terminal may refer to the hardware and software used forcheckouts. A retail POS system typically includes a computer, monitor,cash drawer, receipt printer, customer display and a barcode scanner,and a debit/credit card reader. It can also include a weight scale,integrated credit card processing system, a signature capture device anda customer pin pad device. Many POS monitors use touch-screen technologyfor ease of use and a computer is built in to the monitor chassis forwhat is referred to as an all-in-one unit. The POS system software cantypically handle a myriad of customer based functions such as sales,returns, exchanges, layaways, gift cards, gift registries, customerloyalty programs, and quantity discounts.

The mobile devices 20 a, 20 b may also be referenced as handhelddevices, handheld computers or simply handhelds. These may bepocket-sized computing devices, typically having a display screen withtouch input and/or a miniature keyboard. In the case of the personaldigital assistant (PDA), the input and output are often combined into atouch-screen interface. The mobile devices 20 a, 20 b may also be orinclude iPhones™, iPads™, net books, Android™ phones, E-readers, orother smart phones or other devices. Typically these devices areequipped with cameras or other imaging devices. In embodiments of theinvention, these imaging devices may be implemented to capture receiptimages, which will be more fully explained below. However, in additionalembodiments, the image capture can occur on an alternative device, suchas an ATM, smart watch, smart glasses, or any device including a scanneror imaging device.

The mobile devices 20 a . . . 20 b may store applications including amobile payment application 22 and an expense splitting application 24.The mobile payment application 22 may be an application offered by thefinancial institution 100 or other financial institution. In embodimentsof the invention, the captured receipt may be viewed using augmentedreality. For example, a user may view and process a receipt through aheadset and browser interface. In other embodiments, a user may view andprocess a receipt through an device that employs augmented realityaspects. For example, if an individual has a smart device such as aphone with augmented reality technology, a user may employ the claimedinvention through a projected view of the phone pad without physicallytouching the phone. A smart device, as the name suggests, is anelectronic gadget that is able to connect, share and interact with itsuser and other smart devices. The mobile payment application 22 may havefunctionality such as that offered by Chase QuickPay™. Mobile paymentapplication 22 may allow customers to send payments to businesses orindividuals. In embodiments of the invention payment may be in the formof tokens. The expense splitting application 24 may providefunctionality for allowing users to split expenses in accordance withembodiments of the invention, as will further be described below withreference to FIG. 2.

The user computing devices, 30 a-30 c may be or include any type ofcomputing device. These computing devices 30 a . . . 30 c may allowusers to access the financial institution system 100, These computingdevices enable user access to the receipt management system 80 tofacilitate generation and viewing of reports and also the paymentssystems 90 for receipt and generation of payments and status checkspertaining to payments.

The networks 40, 50, and 60 may be the same or different networks andmay include a wired or wireless local area network (LAN) and a wide areanetwork (WAN), wireless personal area network (PAN) and other types ofnetworks. When used in a LAN networking environment, computers may beconnected to the LAN through a network interface or adapter. Computersmay be connected over the Internet, an Intranet, Extranet, Ethernet, orany other system that provides communications. Some suitablecommunications protocols may include TCP/IP, UDP, or OSI for example.For wireless communications, communications protocols may includeBluetooth, Zigbee, IrDa or other suitable protocol. Furthermore,components of the system may communicate through a combination of wiredor wireless paths.

The transaction processing system 70 automates the handling of datarelated to debit and credit transactions. Data available from the POSabout each transaction are captured, transactions are verified andaccepted or rejected and validated transactions are stored for lateraggregation. Reports may be produced immediately to provide standardsummarizations of transactions and transactions may be moved fromprocess to process in order to handle all aspects of the businessactivity. The POS information may be transmitted to the receiptmanagement system 80 for storage and matching with image data from acaptured receipt and with credit card or other records. Illustrativeexamples of transaction processing systems are described for example, inU.S. Pat. No. 4,877,947 to Mori, U.S. Pat. No. 5,604,802 to Holloway,U.S. Pat. No. 4,375,032 to Uchida, U.S. Pat. No. 4,423,313 to Tanigaki,U.S. Pat. No. 4,594,663 to Nagata, U.S. Pat. No. 4,423,318 to Gotou,U.S. Pat. No. 4,587,379 to Masuda; U.S. Pat. Nos. 5,809,483, and6,039,245 to Symonds.

The receipt management system 80 interacts with the mobile devices 20 tocollect receipt images and manipulates and shares the data collectedover the network 60 with user computing devices 30 and with the mobiledevices 20. Embodiments of the receipt management system 80 are furtherdescribed below with reference to FIG. 9.

FIG. 2 is a block diagram illustrating an expense splitting application200 in accordance with an embodiment of the invention. The expensesplitting application 200 may include multiple software modules executedby a computer processor to perform various functions related tosplitting of expenses. The expense splitting application 200 mayinclude, for example, a receipt capture engine 210, a tagging interface220, an allocation engine 230, a tax handler 240, a tip handler 250, apayment handler 260, and a reimbursement engine 270.

The receipt capture engine 210 operates in conjunction with the mobiledevice processor to capture a receipt image for a transaction andtransform the receipt image to receipt image data. For example, thereceipt capture engine 210 may perform optical character recognition(OCR) in order to transform the image to data. Optionally, the receiptcapture engine may send the captured image over a network to anotherlocation, such as the financial institution system 100 so that the OCRand transformation to data will be performed elsewhere. In embodimentsof the invention, the receipt capture engine 210 is able to capture anyform of receipt. In other embodiments of the invention, the receiptcapture engine can receive input from a user about how to properly parsethe information from a receipt. The receipt capture engine learns froman initial capture and/or input from a user, and is able to effectivelyand properly capture the information from an exact or similar form ofreceipt when presented with an exact or similar form of one or morereceipts thereafter. The receipt capture engine stores the receiptformat in its memory or receipt vault for retrieval at another triggertime. The receipt capture engine may also register a particular form ofreceipt for a merchant via, for example, a merchant name or location andcategorize the receipt by type for later uses. This may allow thereceipt capture engine 210 to easily and effectively parse the receiptwith the expected format in subsequent cycles of receipt capturing.These steps may occur at the mobile device. In embodiments of theinvention, the initial capture may create a temporary webpage where allthe items are listed, and the link can be sent via e-mail, message,application, or other communication medium available to any or allmembers of a party. A quick code may also be generated and inserted intoa member's application prompting them to join. The application mayincorporate special promotions to incentivize party members to join theapplication. These promotions may apply to multiple people in the party,and can be sent via code, token, or other medium. Persons of ordinaryskill would recognize the various methods that may be employed to sharean application. In embodiments of the invention, the merchant may usepromotions to incentivize members to join the application and/or utilizetheir services. For example, a member walking past a candy store mayreceive a discount notification on their application to enter for adiscounted candy purchase. In embodiments of the invention, thetemporary webpage may launch or communicate with an application such asChasePay, Chase Quickpay, and/or any other financial institution'speer-to-peer payment feature.

In embodiments of the invention the receipt capture engine 210 capturesreceipts automatically. For instance, once a merchant provides areceipt, a party member may offer their credit card. Once the creditcard payment is processed, the receipt capture engine auto populateswith the itemized list of purchases for tagging. In embodiments of theinvention, a grocery shopper, for example, will receive an itemized listfor all items purchased at the point of sale transaction through thereceipt capture engine 210. Embodiments of the invention prevent theneed to capture a receipt via, for example, a photograph. In otherembodiments of the invention, the merchant simply sends the receiptdirectly to the one or more party members' application.

Once the transformation is performed, the receipt capture engine 210 maydistribute the data for use in other systems, such as an expensemanagement system, in which the receipt image data is matched with a POStransaction record. The receipt capture engine 210 also may store thedata as well as the image and may utilize the data in various userinterfaces instrumental for expense splitting functionality. Asdescribed herein, the receipt may be viewed using augmented realitytechnology.

The tagging interface 220 provides a tagging interface for a particularpurchase, such as a restaurant check. Thus, the interface will typicallyprovide a list of multiple items included within a purchase. Each itemwill be taggable or selectable to include one or more purchaseridentities. The purchaser identities may be maintained in the mobileapplication or may be extracted from other associated systems.Associated systems may be, for example, e-mail, mobile device contacts,or integrations with a merchant or social media account. Persons ofordinary skill would recognize the various mediums with purchaseridentities that may be integrated with the expense splitting application200. Each user has his or her own purchaser identity, which can be usedfor tagging of purchases. Thus, the tagging interface 220 is interactiveand allows the user of the mobile device to tag each item within apurchase with one or more purchaser names. In embodiments of theinvention, the tagging interface 220 may also tag items based on thegeography of the purchaser. In embodiments of the invention, the tagginginterface allows a member to easily split items. For example, ifeveryone shared an appetizer at a restaurant, a party member can veryquickly and seamlessly split the cost between all the party members.

In embodiments of the invention, the tagging interface 220 allows aparty member to raise any issues with an item's spelling/name, price,quantity, or other attribute of the order. For example, if an incorrectprice is listed on the receipt, a party member has the option ofselecting that item, and requesting a correction. In embodiments of theinvention, the party member may correct the pricing unilaterally, andseek approval from the merchant. The change for approval mayautomatically be sent back to the merchant's point of sale system. Inembodiments of the invention, the merchant has an integrated platformand can approve changes rapidly and efficiently. The merchant mayoptionally make changes and issue a new receipt. The new receipt may bethe entire receipt, or optionally only alter the portion of the receiptfor the party member who disputed the charge. The new changes may besent back to the party member in a digital or physical format. In otherembodiments of the invention, the party member may verbally explain theissue and the merchant may issue a new receipt. In embodiments of theinvention, the new receipt can be recaptured for re-tagging. The newreceipt can also be recaptured as described herein and the tagginginterface 220 can preserve or reload the previously tagged items, sothat the only outstanding items for tagging are the newly changed itemsor items that were not already tagged. An alert or notification mayappear on the application alerting the party members of any changes.These alerts may be in real-time. For example, as soon as the merchantchanges the receipt, the alert and change will appear in real-time onthe party member's application.

The allocation engine 230 may operate on the information entered throughthe tagging interface 220 once each item has been tagged with at leastone purchaser. If an item on the tagging interface is tagged withidentities of three purchasers, the allocation engine will split thecost of the item three ways and allocate one third of the expense toeach purchaser. The allocation engine 230 operates on each itempurchased to perform the allocation accordingly. In embodiments of theinvention, the expense splitting application 200 may geographicallylocate a person using, for example, relevant GPS technology and/or theapplication, and create an intent of purchase before processing anypayments from any party members. In other embodiments, the person may belocated using their place at the table, as described in further detailwith regards to FIGS. 13 and 14. A party member may “approve” the intentto purchase. In embodiments of the invention, a party member may approvea transaction with their itemized items chosen, tagged, or ordered. Oncean item has been accepted or approved by a particular party member, theitem is highlighted, removed, or otherwise accounted for in theapplication to demonstrate that it has been accounted for and/orapproved for payment.

In embodiments of the invention, where multiple people have ordered thesame item, the allocation engine 230 may split the grouped items intosingle items for appropriate approval. For example, where two purchasesof soda have been ordered, the allocation engine 230 can split the iteminto two separate lines.

The tax handler 240 may be provided to split taxes proportionately tothe allocated expenses. For example, if a first purchaser is allocatedtwo thirds of the expenses, the tax handler 240 may determine that twothirds of the tax expense should be paid by the first purchaser,provided that all of the items within the purchase are taxable items. Ifsome of the purchases are not taxable or are not equally taxable, thetax handler 240 may be configured to make this determination and operateaccordingly.

The tip handler 250 may be provided for handling of tips for purchasesat restaurants, hotels, or other venues where tipping is customary. Inembodiments of the invention, each of the multiple purchasers may entera tip. The tip may be entered for example, on the tagging interface. Inalternative embodiments of the invention, the payer may select a tipamount and may allow the tip to be allocated based on percentage ofpurchase. Additionally, in situations in which the tip is alreadyincluded in the bill, such as when a large party dines at a restaurant,the allocation engine 230 may allocate the tip either based on thepercentage of the bill allocated to each purchaser or evenly among thepurchasers. In additional embodiments, the payer may elect atip-handling method from a tip handling interface. The method may be acustomized method or a provided default method.

The payment handler 260 may incorporate or interface with payment system90 operated by the financial institution system 100 in order to allowpayment for the purchase with the mobile device 20. The payment handler260 may allow authorization for and recording of payment for thepurchase. In embodiments of the invention, the payment handler isactivated once all party members have approved the items they selectedor were assigned. In other embodiments of the invention, the paymenthandler is automatically activated once all items are accounted for. Inembodiments of the invention, one party member may pay the merchant, andseek reimbursement of the other party members' allocation from eachrespective party members. The payment handler 260 may seekauthorization, or some form of pre-approval, including via tokenization,prior to paying with a party member's credit card, or withdrawing itfrom a party member's account. Payment can be made directly to themerchant from each party member's application, one or more partymember's application, or alternatively via a single lump sum. Iftokenization is employed, a party-member who has selected and approvedhis items can provide, via an application, text message, e-mail message,or other means, a token of any kind to assign to this bill. This tokenconducts the transfer of the money once the host approves that all lineitems have been filled.

On the other hand, the payment may be pulled from each of the partymembers accounts for the full amount that they owe. Payment may also bepulled from certain party members, while the rest is paid for by one ormore users who then seek reimbursement from the others. Payment may beobtained from each party member at the same or separate times.

The payment handler 260 can account for cash payments or payments madeby financial methods outside of the application, by any party member.The application can still be used to allocate the amount of money thecash or other financial method payer's amount due. The cash or otherfinancial method payment may be made directly with the merchant, and theapplication can reduce the total owed. Alternatively, a party member canretrieve the cash or other financial method payment and simply increasetheir portion of the total bill accordingly. The application allows thepayment handler 260 to tag the methods for which each party member ispaying. As such, a cash payee, for example, will be indicated as such inthe application so as ensure all payment is made.

The reimbursement engine 270 may operate upon payment through thepayment handler 260 to request reimbursement of the payer from eachpurchaser. The reimbursement requests may interact with payment systemsaccessible to each purchaser's mobile device. The reimbursement engine270 may provide reimbursement requests with a selectable option to “PayNow”. Thus, upon receipt of the reimbursement request, purchasers may beimmediately directed to a payment interface so that they can quickly andexpeditiously reimburse the payer. In embodiments of the invention, thepayment interface may tokenize the payment method. In other embodimentsof the invention, the payment interface may execute the payment with themerchant. In embodiments of the invention, a single party member mayscan all the receipts for the bill. For example, a party member may scanall receipts for an entire trip. They may assign the payer to thereceipt as well. For example, while Beth, Anna, and Becky are on a trip,Beth pays for certain items and Anna pays for others. Beth may add allreceipts to the application, even if Anna paid for some, and properlyassign the payor. The tagging interface 260 may be utilized while eachreceipt is uploaded, or a master receipt may be created where tagging ispermitted at any time. A party member may select their own items or asingle party member may assign items. The other functions of theinvention are applied as described herein.

In embodiments of the invention, the reimbursement engine 270 may trackreimbursements and may send reminders if the reimbursements are notreceived within a particular timeframe. The time trigger for sending areimbursement reminder may be set to a default value, or alternativelymay be set by the payer requesting reimbursement. The payer may resetthe time for each purchase or may store a reimbursement time period foruniversal use. In embodiments of the invention, the reimbursement engine270 may interact with a collections system that will take overreimbursement processing if a purchaser fails to reimburse the payer.Ideally, however, both payment and reimbursement can be accomplished inreal time upon completion of the purchase. For example, when paying arestaurant check, the payer may pay with a mobile device. Otherpurchasers may immediately use their own mobile devices to reimburse thepayer. In embodiments of the invention, each user pays the merchant.

FIG. 3 is a flow chart illustrating an expense splitting method inaccordance with an embodiment of the invention. The method begins inS300 and the expense splitting application is implemented by at leastone processor to capture a receipt for a purchase at S310 and transformthe receipt image to receipt image data in S316. As set forth above,transformation of the receipt image to data can alternatively beperformed at the receipt management system. The two systems might thenshare the information over a provided network. In S320, the systempresents a tagging interface allowing the payer and the other purchasersto tag purchased items. Users may select items, draw boxes around them,highlight, underline, or otherwise mark items identified on the receipt.Users may alternatively select particular attributes such as quantity,item detail, and price. In some embodiments, other items, such as taxesand tip, may also be tagged. Once the purchasers have completed thetagging in S320, the system receives the user input from the tagginginterface in S326 and determines in S328 whether all displayed itemshave been tagged. If the displayed items have not been tagged in S328,the system may prompt the user for additional tagging in S330 andpresent the tagging interface again. The tagging interface may be shownwith visual indicators, such as arrows or highlights or other indicatorsadjacent or pointing to items that have not been tagged. If all itemshave been tagged in S328, the system may proceed to perform allocationin S340. The allocation step S340 may be a process with multiple stepsperformed through interaction between the allocation engine, the taxhandler, the tip handler, and other components. After allocation hasbeen performed in S340, payment processing may be performed in S350 uponreceipt of a payer request for payment.

After the payment request has been accepted in S350, the reimbursementengine generates, monitors, and processes reimbursement requests inS370. In embodiments of the invention, the reimbursement requests can beforwarded. Although the payer may forward the reimbursement requestautomatically to one of the purchasers, the purchaser system may beconfigured to automatically forward the reimbursement request to anothersystem. For example, for students, they may have agreements with theirparents to pay for certain types of expenses. Filtering functionalitycould automatically forward the reimbursement requests. Additionally, inembodiments of the invention, if the participants are meeting forwork-related activities, their expenses may be reimbursed by theiremployers. The application may automatically forward the reimbursementrequests based on stored settings. The process ends in S390.

FIG. 4 is a flow chart illustrating a payment processing method S350performed within an expense splitting method in accordance with anembodiment of the invention. In S400, the system provides paymentoptions to users. Those payment options may include credit card, debitcard, check, electronic check, cash or any other form of payment. If thesystem receives a payment request for payment through one of thesemethods in S402, the system forwards the payment request for processingin accordance with the selected method in S420. If no payment request isreceived in S402, the system may continue to prompt the user in S410 andprovide payment options in S400 until the payment request is received.The process ends in S430.

FIG. 5 is a work flow diagram illustrating a reimbursement processingmethod S370 that may be implemented in accordance with an embodiment ofthe invention. In S500, the system may generate and send reimbursementrequests in accordance with the allocation. These requests may begenerated to each purchaser tagging an item. Generation of thereimbursement requests may be triggered by receipt of payment from thepayer. In S510, the system determines if a reimbursement response hasbeen received from each purchaser. If no response has been received inS510, the system may send a reminder to the purchaser in S512 andmonitor for compliance in S520. Compliance may be monitored by settingtime limits for payment and generating reminders when the purchasershave not complied with the time limits. Furthermore, in embodiments ofthe invention, the system may forward overdue accounts to a collectionssystem for collection and enforcement. If the reimbursement response isreceived in S510, the system notifies the payer in S530 and updates thetransaction record to show that reimbursement has been completed inS540. In embodiments of the invention, reimbursement for each purchaserinvolved in a purchase is collectively monitored, such that the systemnotifies the payer both when each reimbursement is received and when allreimbursements have been received. The process ends in S550.

FIG. 6 is a user interface 600 illustrating a payment recipient listthat may be implemented in accordance with an embodiment of theinvention. The user interface 600 may provide multiple tabs 610 forallowing viewing of accounts, payments and transfers, depositing ofchecks, and other options. The payment interface may include a recipientlist 620 including one or more recipients that allows modification ofrecipients at 624 and selection of recipients as shown at 628. A numberof additional guests present for splitting expenses may be illustratedat 630. The additional guests may be added or imported usingfunctionality 624. Other options 640 may also be provided on theinterface. The table setting may also be updated accordingly.

FIG. 7 is a user interface 700 illustrating a method for receipt capturein accordance with an embodiment of the invention. Instructions 710 maybe provided to explain receipt capture to the user. For example, theuser may employ a mobile device camera to capture a receipt which isdisplayed within boundaries 702. Options 750 may be provided tophotograph the receipt and to scroll back to a previous frame.Additional information may be provided at 740. An image of the receipt720 may be shown and camera icon 730 may be used to capture the image.

If the receipt is of a length too great to be captured in a single frameby the mobile device camera, a “long receipt” capture method may be usedto capture an image of the receipt. Such a “long receipt” capture methodis disclosed in co-pending U.S. patent application Ser. No. 13/795,147,which is incorporated herein by reference. The methods of capture arestored in the receipt vault for automatic retrieval.

In embodiments of the invention, the system allows for pre-registrationof all party members before a meal, or may permit changes throughout thecourse of the meal or upon receiving a receipt. In an embodiment of theinvention, the merchant is integrated with the application. As such, themerchant may send the receipt over a network directly to the partymembers who ordered those items. The receipt may be split by theindividual who ordered the item, or it may be whole with the entireparty's orders. In an embodiment of the invention, the items thatweren't split can be sent directly to a single party member who orderedthe item, and the merchant can also send communal items to be split. Ifa mistake is made and another party member's items are sent to the wrongparty member, one or more party members can easily, quickly, andaccurately reassign the items to the correct party member.

FIG. 8 is a user interface 800 illustrating tagging within an expensesplitting method in accordance with an embodiment of the invention. Apayments and transfers tab 810 may be selected from the interface 800. Acaptured receipt 802 may have its data imported into the interface 800.Purchased items 840 may appear in taggable format on the interface 800.Assignments for each purchased item are shown at 830. Totals for eachpurchaser are shown at 850. The interface provides the payer with anopportunity to send a payment via QuickPay™ at 860. Other paymentmethods may also be implemented. Additional resources 870 may be reachedfrom the payment interface 800. The basic flow would be users take apicture of the receipt which is translated to text, then users tag usersto each item (either all to split evenly or specific users) and thetotals are calculated and the option to send a QuickPay™ request willshow up so that the user can pay the entire bill and have the friendspay back via QuickPay™.

As an exemplary scenario of use for the expense splitting method, whenJane and her roommate Sophie go out to dinner, Sophie typicallypurchases two glasses of wine and steak and lobster. Jane, on the otherhand, drinks water and eats only a salad. Jane and Sophie then share adessert. Thus, when the check arrives, Jane does not want to share inthe expense equally and Sophie is willing to pay a greater share of thebill corresponding to her purchases. Accordingly, Jane accesses thecheck splitting application on her smart phone. The application promptsJane to capture a photograph of the receipt. The system operates on thecaptured photograph to have the purchased items on the receipt imagetransformed to text to render them interpretable as data. Once the itemsare translated to text, the system produces the tagging interface andJane and Sophie can tag each item accordingly. Thus, Sophie tags the twoglasses of wine, the steak and the lobster. Jane tags the salad. BothSophie and Jane tag the dessert. The application then automaticallysplits the tax based on their respective bills. Both Sophie and Janehave the opportunity to enter a tip. The application then provides anoption for Jane to send a QuickPay™ request to Sophie for her allocatedexpenses. Jane can also pay the entire bill through her application andallow the application to generate a reimbursement request for Sophie toreimburse Jane via QuickPay™.

The restaurant bill is merely an example. People often share expenses inother situations, such as gas and food for road trips and householdgoods for roommates. The mobile application can also be advantageous inthese situations to avoid the necessity for passing cash back and forth.Embodiments of the invention are applicable to any instances wherepurchases are made, are itemized, and/or need to be split.

While the application may operate on a paper receipt, it can also beused for electronic receipts. In this instance, the receipt could betransmitted to the user's mobile device and there would be no need forimage capture. If the electronic receipt is in image format, it also maybe transformed to data. In embodiments of the invention, the receipt maybe at the time of the transaction, as described herein. For example, apayer purchasing flowers and candy from a convenient store mayautomatically obtain an itemized receipt at the time his payment istransacted. The payment may be through use of a credit card, paymentthrough a mobile device or smart watch, or any other conceivablefinancial instrument, including tokenization.

Additionally, while the application is useful at the point of purchase,it may also be possible to pay the entire bill, send the receipt tostorage, and request reimbursement at a later time. Any stored receiptscan also be split later or stored for historical purposes. This featureis also useful when only one member of the group has a cell phone.Reminders can be triggered to the other members to make reimbursementsat a later time.

As described herein, embodiments of the invention allow for machinelearning. Embodiments of the invention also integrate machine learningregarding purchase patterns with notifications to the user. For example,if a payer purchases certain items in any conceivable pattern, an alertor notification will appear on the payer's application reminding them tobe mindful of an upcoming purchase. The notifications may be, forexample, about a recurring purchase based on categorization of theitemized receipts. For example, a user purchasing milk every week may bereminded to purchase milk at the proper increment. In embodiments of theinvention, the notifications may also be integrated with a user'scalendar application, and include reminders for purchases that need tobe made. For example, a wedding calendar input may trigger anotification for purchasing a present. Merchant's incentives or othercoupons or discounts available may link to these notifications. Thenotification may alternatively be in the form of an SMS message, e-mailmessage, or linked to social media or any peer-to-peer messaging system.In embodiments of the invention, the payer may turn off thesenotifications.

FIG. 9 is a block diagram illustrating a receipt processing and expensemanagement system 900 that may be implemented in accordance with anembodiment of the invention to interact with and store information fromthe mobile payment application and expense splitting application. Userinterface tools 940 may communicate over the aforementioned networkswith users and external systems. A receipt collection engine 920 managesreceipt intake and provides receipts to a receipt management system 930for processing and a receipt vault 910 for storage. The receiptmanagement system 930 may also access additional internal or externaldatabases 950 as will be further explained below. The receipt managementsystem 900 may operate interactively to receive information from andtransmit information to the expense splitting application 200.

The receipt vault 910 stores receipts collected by the receiptcollection engine 200. The receipt collection engine 920 may receive theimages from the mobile or other devices and prepares them for storage inthe receipt vault 910. For example, the receipt collection engine 910may receive the captured receipts from the expense splittingapplication. While in some embodiments of the invention, the expensesplitting application 200 may convert the captured receipt image toreceipt data, other embodiments may permit the captured receipt image tobe transmitted to the expense management system for transformation ofthe receipt image to receipt data. The receipt vault 910 may store bothreceipt images and receipt image data.

Thus, the receipt collection engine 920 may operate to import receiptsand store them in the receipt vault, match receipts with POS and otherdata, perform OCR to transform the receipt image to receipt data, storethe receipt image in the receipt vault, and allow user management of thecaptured and stored data.

Importation of the captured receipt image may depend upon thecharacteristics of the captured receipt image or the electronic receiptprovided by a merchant. The receipt collection engine may receive userrequests to match the receipt image with additional data such as the POStransaction record. Alternatively, the receipt management system 930 maybe automated to perform this function upon the performance of OCR on thereceipt. OCR components may be provided to operate on the receipt imagein order to translate the scanned images of handwritten, typewritten orprinted text into machine-encoded text. OCR makes it possible to editthe text, search for a word or phrase, store it more compactly, displayor print a copy free of scanning artifacts, and apply techniques such asmachine translation, text-to-speech and text mining to it. The systemmay be capable of reproducing formatted output that closely approximatesthe original scanned page including images, columns and othernon-textual components. The system may also be capable of grouping andconverting similar receipts similarly without prompting from a user.

Once the information from the receipt is collected and converted todata, the system enables the purchaser to categorize purchases, manageprojects by tagging purchases across categories, and to createcustomized reports. Alternatively, the system may be configured toautomatically perform some or all of these functions based on theinformation gathered from the receipt.

The receipt collection engine 910 captures information that may only beavailable on the receipt and is likely not available in the POS record.For example, the receipt may include various characteristics of thepurchase including the exact items purchased, the size of each item, thequantity of each item, the price of each item, discounts from the usualprice for each item, SKU, department, sales tax, and total amount ofdiscount for the purchase. The receipt may further include informationon payment method, such as cash, check, credit card, debit card, andsufficient information to identify the particular debit or credit card.Each card account may be held at the same or different banks.

The receipt management engine 930 uses information stored in the receiptvault 910 and organizes the information in any manner requested by thesystem users. Thus, with this information, the system enables customersto search across accounts for receipts and figure out which card orother payment method they used to make a purchase. This may apply toaccounts managed by multiple institutions. The receipt vault 910 may besearched by customers and may provide multiple filtering categories toenable simplified management. Furthermore, in some embodiments,customers may have access to receipts for accounts of family members inorder to allow for household reporting and management. The receiptmanagement engine 930 may provide functionality for tagging,categorization, searching, report generation, return management,exception handling, coupon generation, returns management, productinformation management, tax handling, and warranty management. Thisfunctionality is described in greater detail in co-pending applicationSer. No. 13/165,929 which is incorporated herein by reference.

With respect to tagging, in addition to the functionality describedabove pertaining to the tagging of particular purchases with a purchaseridentity, the system may allow users to tag a receipt across multiplecharacteristics. For example, every receipt where a specified creditcard was used may be tagged for that credit card. Every receipt relevantto a food purchase may be tagged for consumables. Ticket purchases maybe tagged as entertainment. Receipts may be tagged across payment methodsuch as debit, credit, cash, or check, a particular account number,category of goods or services, price, discount, amount thresholds, dateranges, payment methods such as debit or credit, banks, and accounts,such as specific account numbers.

Categorization components may operate to automatically categorize thereceipt data based on the purchase. This categorization may be typicallybe across the category of goods, but may account for other factors. Forexample, as set forth in co-pending application Ser. No. 11/952,457,transactions can be categorized by project.

The receipt management engine 930 provides search functionality thatallows searching across categories and tags in accordance with a userrequest. For example, a system user may want to see all transactionswith total sales amounts between $100 and 200. Alternatively, the systemuser may seek all purchases made with credit cards. System users cancombine these characteristics to search for all sales for amountsbetween $100 and $200 paid with credit cards, and can further excludepurchases for travel from the results if desired.

The receipt management engine 930 additionally provides reportfunctionality for producing comprehensive reports in accordance with auser request. For example, commands may be entered through the userinterface to produce reports or the search engine may generate output tocreate reports. The reports may, in embodiments of the invention, be inspreadsheet format, such as for example, Microsoft Excel, or mayalternatively be displayed for example in CSV or flat text format.Search criteria may be implemented on the report to search to and fromvarious dates. Furthermore, reports may be generated automatically inaccordance with pre-set parameters, such as monthly, quarterly, oryearly. The pre-set parameters alternatively may trigger generation of areport upon reaching a pre-set expenditure threshold. Other triggers mayalso be implemented. Generated reports are preferably also searchablebased on user-selected parameters. Reports may be generated for selectedcategories or selected tags or both selected categories and selectedtags.

The receipt management system 930 may include an exception handlerconfigured to accept manual entry when issuance of an electronic receiptor a paper receipt fails such that an image cannot be captured. Forexample, the user may manually enter a type of purchase, date ofpurchase, location of purchase, and amount of purchase. Theabove-described matching functionality will ultimately match themanually entered sale with the POS record. Manually entered informationmay also be utilized by the expense splitting system when appropriate.Additionally, when traditional receipt generation fails, the user maycapture an image at the point of purchase and enter the image into thesystem. For example, if a gas pump fails to produce a receipt, thecaptured image may include a gas pump with an amount of sale. In otherexamples, the captured image may include another type of automateddispenser, an image of a cash register, or of a product purchased. Theimage may ultimately be matched by the system with the appropriate POSrecord based on manually entered details of the purchased processedthrough the exception handler. In embodiments of the invention, theimage and/or matched record may be exported to online storage in adisplayed database or other storage area for later retrieval.

The receipt management engine 930 may also include coupon functionalityfor generating user-specific coupons based on the specific itemspurchased by the users. These coupons may be found in an external orinternal database located in a storage area. Further, the coupons may beprovided to the system by merchants upon registering a purchase, basedon the items purchased. These coupons may be printable or scannable atthe point of purchase for predetermined products. In operation, thecoupon generator may scan stored receipts and perform a search ofcoupons based on the items purchased. The receipts may be scanned uponentry into the vault or periodically at pre-set intervals.

The receipt management engine 930 may also include software for handlingreturns. A returns handler is operable to enable a purchaser to use thecaptured receipt image matched with the POS record to execute a return.In operation, a customer may select a receipt and transmit data from amobile device to a POS terminal. The POS terminal may run compatiblesoftware to execute a return. Upon return of an item, the returnshandler may delete the records of the returned item or may tag andcategorize the item as returned and store the purchase and returninformation for the returned item in a designated location.

The receipt management engine 930 may also incorporate productinformation handling functionality that accesses internal or externaldatabases to locate information about a purchased product and make thatinformation easily accessible to the purchaser. For example, the systemmay locate accessories, such as, for example, appropriate batteries fora tool purchased, a suitable bulb for a purchased light fixture, or inkcartridges for a purchased printer, and may provide links to theseproducts to the purchaser through a provided interface. Furthermore, theproduct information handler may locate servicing information. Forexample, if a service, such as an oil change is purchased for a car, theproduct information handler may locate the next required servicemilestone and provide the purchaser with an alert before the nextservice is required. The product information handler may further locateinstruction manuals for purchased products and provide a selectable linkto the instruction manual. The information may be located throughavailable external and/or internal databases, such as databases 950shown in FIG. 9. Thus through the provided system, a purchaser's recordis complete with all associated product information. In embodiments ofthe invention, the system offers all of this information through a userinterface available at a web site accessible to system users such aspurchasers. Additional product information may include a photograph ofthe product for storage and association with other collected productinformation.

The receipt management engine 930 may also incorporate tax processingfunctionality. The system may register a purchase if that purchase haspotential tax consequences. For example, if a purchase is made for arental property and is properly categorized, the system may save theinformation for additional tax processing. Further, if a transaction isa charitable donation, the system may store this information forsubsequent tax processing. In embodiments of the invention, the systemcategorizes stored tax information so as to be easily accessible tosystem users.

Additionally, the receipt management engine 930 may store warrantyinformation related to purchased products and provide a link to thewarranty information in association with the stored receipt and POSrecord. Purchasers may be provided with alerts or reminders prior to theexpiration of a warranty and/or offers to extend the warranties. Thereceipt management system may combine warranty and product informationto provide a comprehensive interface for each purchased product, so thatusers can view purchase information, warranty information, instructionmanuals, and accessories simultaneously. In embodiments of theinvention, warranty information can be integrated with an onlinecalendar. Thus, based on a purchase date, warranty expiration dates andrenewal opportunities may be integrated with the calendar.

Thus, embodiments of the invention provide a system and method forcapturing an image of a receipt, attaching the receipt to a transaction,and transforming a receipt image to receipt image data, for example byperforming OCR or other process that can transform an image to data onthe receipt. The data encapsulated through the transformation processprovides sufficient information for the system to categorize thetransaction, convert the transaction to data, and tag the transaction.Using this information, the system can create customized reports withinparameters established by the purchaser or predetermined by the system.Furthermore, the data enables real time expense splitting amongpurchasers and enables real time payment and reimbursement. As explainedabove, various software modules can be executed by one or more computerprocessors to operate to retrieve information based on recordedpurchases and offer enhanced functionality to system users.

While image capture can be integrated with the system, the system mayalso operate on electronic receipts provided by a merchant or onreceipts transferred from other systems, such as the expense splittingsystem, and these receipts may be stored in the receipt vault 910. Forexample, at checkout, a purchaser may be asked whether an electronicreceipt or paper receipt is preferred. If an electronic receipt ispreferred, the purchaser may receive an electronic receipt directly fromthe merchant and enter this receipt into the system. Furthermore, thesystem is capable of operating on electronic receipts received when apurchaser engages in online transactions. In this instance, customersmay electronically transmit the receipt via email, by enteringinformation into the user interface 940, which may be available on areceipt management website, or by any other method.

The user interface tools 940 interact with user systems to allow accessto reports and data generated by the receipt management system. The userinterface tools 240 facilitate operation of the other components of thesystem through manual intervention. Furthermore, the user interfacetools 940 facilitate viewing of data and reports, thereby enabling usersto view the record. In preferred embodiments of the invention, purchasesdisplayed on the user interface should be represented by a selectablelink, such that selection of the link will provide additional detail onany item presented. In embodiments of the invention pop-up windows maybe implemented to display selected data, although other designs arewithin the scope of the invention.

In embodiments of the invention, the user interface tools 940 areaccessible to customers through a web site to enable viewing oftransaction break down and customized reports. This may include detailedexpense splitting information processed through the mobile expensesplitting application. Customers may enter the captured images into thesystem through the website to implement the receipt collection engine oralternatively, an application accessed through the user computing deviceimplemented by the customer may operate on the captured image. The imageof the receipt may serve as the actual receipt of record back to themerchant so that customer could dispose of the paper receipt and printor show the electronic receipt on a mobile device in order to returnmerchandise or exercise warranty rights.

FIG. 10 is a work flow diagram illustrating receipt managementprocedures in accordance with an embodiment of the invention. In step 1,a mobile device user may import a transaction record. In step 2, themobile device user may implement the mobile device to take an image ofthe receipt. In step 3, the mobile device user may attach the receipt tothe transaction record through functionality provided in the receiptmanagement system. The mobile device user may also implement the receiptmanagement system to categorize the transaction in step 4 and tag thetransaction in step 5. Categorization may include, for example, puttingthe transaction in a category such as travel, entertainment, dining,clothing, household, etc. Furthermore, categories may include variousprojects as set forth in co-pending application Ser. No. 11/952,457,filed on Dec. 7, 2007, which is hereby incorporated by reference.Tagging of the transaction may include associating the transaction withmultiple identifiers or characteristics. The mobile device user then mayallow the receipt management system to operate on the transaction byperforming optical character recognition (OCR) on the receipt andconverting the transaction to data in step 6. In step 7, the receiptmanagement system generates reports as requested by the mobile deviceuser. The reports may provide budget tracking in order to assistcustomers with adherence to realistic goals. The order of the stepsillustrated may be altered in any desired manner. Thus, the receiptmanagement system collects, stores, and organizes receipts. Mobiledevice users may have easy access to receipts and avoid the hassle ofstoring hard copies of receipts. Mobile users implementing the expensesplitting system can enter their purchases into the receipt managementsystem for enhanced functionality and subsequent retrieval.

FIG. 11 is a work flow diagram illustrating procedures for creating atravel report in accordance with an embodiment of the invention. In thisembodiment, employee users of the system may save time by capturingimages of receipts for automatic importation in corporate travel andexpense software. In step 1, a mobile device user may import atransaction record. In step 2, the mobile device user may implement themobile device to take an image of the receipt. In step 3, the mobiledevice user may attach the receipt to the transaction record. The mobiledevice user may also implement the receipt management system tocategorize the transaction in step 4 or may allow the system toautomatically categorize the transaction. In this instance, theillustrated categorization is by trip. The mobile device user may alsoimplement the receipt management system to tag the transaction in step5. In step 6, the receipt management system generates reports asrequested by the mobile device user. The order of the steps illustratedmay be altered in any desired manner.

Embodiments of the invention have wide applicability to corporatesystems as employees may have receipts obtained during business travelautomatically imported into travel and expense software utilized by theemployer. The system thereby enables improved management of travelexpenses by employees by collecting, storing, and organizing thereceipts. Travel may be managed by tagging of purchases acrosscategories. Furthermore, employees traveling together may utilize theexpense splitting system in combination with the receipt managementsystem in order to manage all expenses during a corporate trip.

FIG. 12 is a flow chart illustrating a method for receipt management inaccordance with an embodiment of the invention. The process begins inS1200 and the transaction is completed at the POS in S1204. The receiptmanagement system receives the transaction record in S1206 and the imageof the receipt in S1208. The image may be transmitted, for example,through a user's mobile device. In 51210, the received POS transactionrecord may be matched with the image of the receipt. In S1220, OCR maybe performed on the receipt. The system may categorize the transactionin S1230, convert the transaction to data in S1234, and tag thetransaction in S1238. In S1250, the system may store information andgenerate reports in the manner requested by the system user. The orderof the steps is merely exemplary and the order may be altered in anymanner that might be apparent to one skilled in the art.

FIG. 13 is an exemplary embodiment of an expense splitting application200, as explained herein, additionally comprising a table setting engine1400.

FIG. 14 is an exemplary embodiment of a table setting engine 1400comprising an exemplary table setting in a merchant's venue. Users 1300. . . 1312 may be seated at table 1314. Persons of ordinary skill wouldunderstand that tables can seat anywhere from 0 to an unlimited numberof people, depending on the configuration of the table, limited only bythe capacity and rules of the merchant. Persons of ordinary skill wouldalso appreciate that tables can be configured in various shapes, withseats able to be determined by the merchant or the party members. Inembodiments of the invention, the mobile device comprising the userinterface may allow a user to quickly draw out the shape of the tableand assign party member identities to each seats at the table. The tablesetting engine comprises a database with various common tableconfigurations for a user to pick from when drawing the table. Inembodiments of the invention, the user may optionally hand-draw andstore the configuration for future visits. In other embodiments of theinvention, the merchant may autopopulate the table configuration via themerchant's integration with the application. Embodiments of the tableconfiguration may be changed based on last-minute additions to theparty. Furthermore, identities associated with a particular seat mayquickly be changed if a party member switches seats. This especiallycomes in handy where party members have pre-registered before the meal,as described herein. Accordingly, the merchant's server can assignordered items to each pre-registered member based on their seatlocation, which is also integrated in the application. In thisembodiment, each of the party member's item is already divided by theorderee, and therefore does not require tagging by the party member.Items that are split can be assigned to one party member, who can thentag the individuals who are sharing, can be split evenly amongst allmembers by the merchant, or can be sent as an unassigned item to betagged by the party members.

The preregistration can be through any application, and the mobilepayment application 22 and expense splitting mobile application 24 canbe configured to import data from any compatible database or applicationfor integration therein. FIG. 15 is an exemplary embodiment of anexpense splitting mobile application 24 comprising various merchants fora party member to choose from. These merchants have integrated with theapplication and thus have enhanced capabilities as described herein. Themerchants will populate on the application based on the geography of theparty-member and the merchant. A party member can select a merchant topreregister, or alternatively seek a reservation. An applicant who makesa reservation can share the reservation with other party members who canthen register as well.

FIG. 16 is an exemplary embodiment of a merchant menu 1600 that may belinked to the merchant account. Any or all items of a merchant's menu1600 may be interactive. For example, a party member can select an itemfrom a merchant menu 1600 to obtain further information about that itemin an item information window 1602. The item information window 1602 mayinclude, for example, ingredients, calories, and price. A merchant maycustomize this as they choose. In embodiments of the invention, a partymember can choose to order the item by clicking a button next to theitem in the menu 1600 or clicking the order button in the iteminformation window 1602. There, the party member can add any additionalnotes. If the merchant is unable to acquiesce to the party member'srequest, the merchant may reject the order, and/or discuss the orderwith the party-member. In embodiments of the invention, a party-membermay be able to upload pictures of the selected item, or browse picturesof other user uploaded items. Photos of all party members mayautomatically be grouped and or organized into a collage for public orprivate display. Party-members may also post reviews of particular itemsor rate the items, or browse the reviews or ratings of other users. Thephotos, reviews, and ratings can be associated with each itemindividually, or the merchant as a whole. The merchant has the option toremove certain photos or reviews. In embodiments of the invention, wherea merchant removes photos or reviews, the application will indicate assuch. The merchant may also respond to certain photos or reviews, at itsdiscretion. The merchants may also have separate merchant pages withlinks to the ratings, reviews, and photos posted. Users may also postdirectly to the merchant page.

A party member's transaction information can also be uploaded and sharedpublicly or privately amongst the members who attended for laterretrieval. For example, if a party member wants to remember what theyordered a previous time, they can retrieve the group's previous purchaseprivate or public publication of the transaction details of the previouspurchase. Users may also leave graphical or textual or pictoralcomments. The comments can disclose the dollar amount, location, orother information. Historical information linked to a user and merchantmay be retrievable at any time, or deleted by the user. The historicalinformation can be stored in the receipt vault or application publiclyor privately.

Merchants may be encouraged to create an account and/or integrate withthe application through various incentives or programs offered by theapplication creator. The information may optionally be imported fromother applications or systems that have this data publicly available.

FIG. 17 is an exemplary embodiment of a merchant interface 1600 wherebya merchant can monitor the items ordered and payments made through aparty's mobile payment application 22 and expense splitting mobileapplication 24. A merchant may monitor each table 1314 . . . 13 nn,where n is the number of tables at the merchant's venue, for outstandingpayment and orders. For example, receipt or bill 1602 may apply to table1314. The merchant's system 1600 can quickly and effectively obtainpayment and understand what balances remain. The merchant's system isalso capable of taking and placing orders for each particular table. Inembodiments of the invention, the merchant may request payment, whichsends a notification to one or more party members' application(s) aboutthe payment. The merchant may alternatively communicate with the partyvia messaging through the applications as well. The merchant may be ableto communicate a wait time until the meal or service is completed.

The embodiments of the invention can be applied to hotel rooms,amusement parks, or any other service whereby bills are split. Theembodiments of the invention can be used, for example, to split the costof a taxi, a rental car, or a cabin. Persons of ordinary skill wouldrecognize the various services the invention can apply to.

It is likely that multiple computing systems or devices will be utilizedto implement the method and system in accordance with embodiments of theinvention. Each computing system may include a processing unit, aperipheral interface, a user input interface, a system bus, a systemmemory, a network interface, a memory interface, and any othercomponents. Computers typically include a variety of computer readablemedia that can form part of the system memory and be read by theprocessing unit. By way of example, and not limitation, computerreadable media may comprise computer storage media and communicationmedia. The system memory may include computer storage media in the formof volatile and/or nonvolatile memory such as read only memory (ROM) andrandom access memory (RAM).

A basic input/output system (BIOS), containing the basic routines thathelp to transfer information between elements, such as during start-up,is typically stored in ROM. RAM typically contains data and/or programmodules that are immediately accessible to and/or presently beingoperated on by processing unit. The data or program modules may includean operating system, receipt management components, other programmodules, and program data.

As described above, embodiments of the system of the invention andvarious processes of embodiments are described. The system of theinvention or portions of the system of the invention may be in the formof a “processing machine,” i.e. a tangibly embodied machine, such as ageneral purpose computer or a special purpose computer, for example. Asused herein, the term “processing machine” is to be understood toinclude at least one processor that uses at least one memory. The atleast one memory stores a set of instructions. The instructions may beeither permanently or temporarily stored in the memory or memories ofthe processing machine. The processor executes the instructions that arestored in the memory or memories in order to process data. The set ofinstructions may include various instructions that perform a particulartask or tasks, such as any of the processing as described herein. Such aset of instructions for performing a particular task may becharacterized as a program, software program, or simply software.

As noted above, the processing machine, which may be constituted, forexample, by the particular system and/or systems described above,executes the instructions that are stored in the memory or memories toprocess data. This processing of data may be in response to commands bya user or users of the processing machine, in response to previousprocessing, in response to a request by another processing machineand/or any other input, for example.

As noted above, the processing machine used to implement the inventionmay be a general purpose computer. However, the processing machinedescribed above may also utilize (or be in the form of) any of a widevariety of other technologies including a special purpose computer, acomputer system including a microcomputer, mini-computer or mainframefor example, a programmed microprocessor, a micro-controller, aperipheral integrated circuit element, a CSIC (Consumer SpecificIntegrated Circuit) or ASIC (Application Specific Integrated Circuit) orother integrated circuit, a logic circuit, a digital signal processor, aprogrammable logic device such as a FPGA, PLD, PLA or PAL, or any otherdevice or arrangement of devices that is capable of implementing thesteps of the processes of the invention.

The processing machine used to implement the invention may utilize asuitable operating system. Thus, embodiments of the invention mayinclude a processing machine running the Microsoft Windows™ Vista™operating system, the Microsoft Windows™ XP™ operating system, theMicrosoft Windows™ NT™ operating system, the Windows™ 2000 operatingsystem, the Unix operating system, the Linux operating system, the Xenixoperating system, the IBM AIX™ operating system, the Hewlett-Packard UX™operating system, the Novell Netware™ operating system, the SunMicrosystems Solaris™ operating system, the OS/2™ operating system, theBeOS™ operating system, the Macintosh operating system, the Apacheoperating system, an OpenStep™ operating system or another operatingsystem or platform.

It is appreciated that in order to practice the method of the inventionas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing as described above is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the invention, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the invention, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories of the invention to communicate with anyother entity; i.e., so as to obtain further instructions or to accessand use remote memory stores, for example. Such technologies used toprovide such communication might include a network, the Internet,Intranet, Extranet, LAN, an Ethernet, or any client server system thatprovides communication, for example. Such communications technologiesmay use any suitable protocol such as TCP/IP, UDP, or OSI, for example.

As described above, a set of instructions is used in the processing ofthe invention. The set of instructions may be in the form of a programor software. The software may be in the form of system software orapplication software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject oriented programming. The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of the invention may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments of the invention. Illustratively, the programminglanguage used may include assembly language, Ada, APL, Basic, C, C++,COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX,Visual Basic, and/or JavaScript, for example. Further, it is notnecessary that a single type of instructions or single programminglanguage be utilized in conjunction with the operation of the system andmethod of the invention. Rather, any number of different programminglanguages may be utilized as is necessary or desirable.

Also, the instructions and/or data used in the practice of the inventionmay utilize any compression or encryption technique or algorithm, as maybe desired. An encryption module might be used to encrypt data. Further,files or other data may be decrypted using a suitable decryption module,for example.

As described above, the invention may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software for example, whichenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set ofinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in the invention may take on any of a variety of physicalforms or transmissions, for example. Illustratively, the medium may bein the form of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, a EPROM, a wire, a cable, a fiber,communications channel, a satellite transmissions or other remotetransmission, as well as any other medium or source of data that may beread by the processors of the invention.

Further, the memory or memories used in the processing machine thatimplements the invention may be in any of a wide variety of forms toallow the memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for example.

In the system and method of the invention, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement the invention.As used herein, a user interface includes any hardware, software, orcombination of hardware and software used by the processing machine thatallows a user to interact with the processing machine. A user interfacemay be in the form of a dialogue screen for example. A user interfacemay also include any of a mouse, touch screen, keyboard, voice reader,voice recognizer, dialogue screen, menu box, list, checkbox, toggleswitch, a pushbutton or any other device that allows a user to receiveinformation regarding the operation of the processing machine as itprocesses a set of instructions and/or provide the processing machinewith information. Accordingly, the user interface is any device thatprovides communication between a user and a processing machine. Theinformation provided by the user to the processing machine through theuser interface may be in the form of a command, a selection of data, orsome other input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod of the invention, it is not necessary that a human user actuallyinteract with a user interface used by the processing machine of theinvention. Rather, it is also contemplated that the user interface ofthe invention might interact, i.e., convey and receive information, withanother processing machine, rather than a human user. Accordingly, theother processing machine might be characterized as a user. Further, itis contemplated that a user interface utilized in the system and methodof the invention may interact partially with another processing machineor processing machines, while also interacting partially with a humanuser.

Accordingly, embodiments of the invention provide a system forallocating each item on a receipt so that only the appropriate partiesbear the expense. Furthermore, embodiments of the invention enable theparties splitting the expense to quickly and efficiently electronicallysettle their finances between one another. Embodiments of the inventionfurther enable enhanced record keeping and reporting functionality.

While particular embodiments of the invention have been illustrated anddescribed in detail herein, it should be understood that various changesand modifications might be made to the invention without departing fromthe scope and intent of the invention.

From the foregoing it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages, which are obvious and inherent to the system andmethod. It will be understood that certain features and sub-combinationsare of utility and may be employed without reference to other featuresand sub-combinations. This is contemplated and within the scope of theappended claims.

1. A computer-implemented expense splitting method for allowing a payerto divide expenses among multiple purchasers, the method comprising:storing, in at least one computer memory, payer data and expensesplitting instructions; accessing the computer memory with at least onecomputer processor and executing the instructions to perform stepsincluding: transforming a captured receipt image to purchase data;storing the captured receipt image format in a receipt vault; providingan interactive user interface displaying a setting wherein a payerchooses a location at the setting and a merchant's entries correspondingto purchases; allocating a percentage or monetary amount of each entryto at least one purchaser based on the tagging or setting; calculatingan amount due from each purchaser based on the allocation; providing apayment interface for allowing online payment from the payer for a totalor partial amount of purchase.
 2. The method of claim 1, furthercomprising capturing the receipt image with a mobile device.
 3. Themethod of claim 1, wherein the interactive user interface display mayutilize augmented reality technology.
 4. The method of claim 1, whereintransforming the captured receipt image to receipt data comprisesperforming optical character recognition.
 5. The method of claim 1,wherein transforming the captured receipt image to receipt datacomprises receiving an itemized list of items purchased from a merchant.6. The method of claim 1, wherein the itemized list of items purchasedis sent automatically to the interactive user interface.
 7. The methodof claim 1, wherein the purchases correspond to items on a restaurantbill.
 8. The method of claim 1, further comprising facilitating onlinepayment in real time through the payment interface directly to amerchant.
 9. The method of claim 1, further comprising generating areimbursement request requesting each purchaser to reimburse the payerfor the amount due from the purchaser upon receipt of a payment request.10. The method of claim 1, further comprising storing the purchase dataand receipt image in an expense management system.
 11. The method ofclaim 1, further comprising providing a reimbursement request interfacefor selecting purchasers.
 12. The method of claim 11, wherein the systemautomatically generates reimbursement requests based on the payer'sallocation.
 13. The method of claim 1, further comprising matching thereceipt image and purchase data with a POS transaction record andstoring the information in an expense management system.
 14. The methodof claim 1, further comprising an interactive user interface foruploading pictures, reviews, and ratings of the items or the merchants.15. The method of claim 1, wherein the setting is automatically set bythe payer's GPS location, Bluetooth Low Energy, iBeacon, or Bluetooth4.0 technology.
 16. A computer-implemented expense splitting system forallowing a payer to divide expenses among multiple purchasers, thesystem comprising: at least one computer memory storing payer data andexpense splitting instructions; at least one computer processoraccessing the computer memory and executing the instructions to performsteps including: transforming a captured receipt image to purchase data;storing the captured receipt image format in a receipt vault; providingan interactive user interface displaying a setting wherein a payerchooses a location at the setting, and a merchant's entriescorresponding to purchases, and further providing a tagging option fortagging each of the entries with an indicator of at least one purchaseridentity; allocating a percentage or monetary amount of each entry to atleast one purchaser based on the tagging or setting; calculating anamount due from each purchaser based on the allocation; providing apayment interface for allowing online payment from the payer for a totalor partial amount of purchase.
 17. The system of claim 16, furthercomprising capturing the receipt image with a mobile device.
 18. Thesystem of claim 16, wherein the interactive user interface display mayutilize augmented reality technology.
 19. The system of claim 16,wherein transforming the captured receipt image to receipt datacomprises performing optical character recognition.
 20. The system ofclaim 16, wherein transforming the captured receipt image to receiptdata comprises receiving an itemized list of items purchased from amerchant.
 21. The system of claim 16, wherein the itemized list of itemspurchased is sent automatically to the interactive user interface. 22.The system of claim 16, wherein the purchases correspond to items on arestaurant bill.
 23. The system of claim 16, further comprisingfacilitating online payment in real time through the payment interface.24. The system of claim 16, further comprising triggering thereimbursement requests upon receipt of a payment request.
 25. The systemof claim 16, further comprising storing the purchase data and receiptimage in an expense management system.
 26. The system of claim 16,further comprising providing a reimbursement request interface forselecting purchasers.
 27. The system of claim 26, wherein the systemautomatically generates reimbursement requests based on allocation. 28.The system of claim 16, further comprising matching the receipt imageand purchase data with a POS transaction record and storing theinformation in an expense management system.
 29. The system of claim 16,further comprising an interactive user interface for uploading pictures,reviews, and ratings of the items or the merchants.
 30. The system ofclaim 16, wherein the setting is automatically set by the payer's GPSlocation, Bluetooth Low Energy, iBeacon, or Bluetooth 4.0 technology.31. A computer-implemented expense splitting method for allowing a payerto divide expenses among multiple purchasers, the method comprising:storing, in at least one computer memory, payer data and expensesplitting instructions; accessing the computer memory with at least onecomputer processor and executing the instructions to perform stepsincluding: transforming a captured receipt image on a mobile device topurchase data; creating a record of the expenses in an expensemanagement system, wherein creating a record includes, matching thepurchase data for each captured receipt image with a corresponding POStransaction record, categorizing the purchase data into one of multiplecategories, and storing the purchase data in a receipt vault; providinga user interface on the mobile device displaying entries correspondingto purchases, and further providing an option for altering the entries,or uploading photos or ratings for each of the entries.
 32. The methodof claim 31, wherein transforming the captured receipt image to receiptdata comprises receiving an itemized list of items purchased from amerchant.
 33. The method of claim 31, further comprising facilitatinggeneration of reports illustrating an expense breakdown, wherein thereports are generated based on user preferences.
 34. The method of claim31, further comprising importing the receipt image from a mobile devicehaving image capture capabilities.
 35. The method of claim 31, furthercomprising implementing optical character recognition for transformingthe receipt image to receipt data.
 36. The method of claim 31, furthercomprising providing an interface for tagging the receipt data acrossreceipt characteristics.
 37. The method of claim 31, further comprisingcategorizing each receipt image into one of multiple categories